|
Assemble Testing Team
| The test team should be organized concurrently with the development team. The purpose of the test team is to perform
verification and validation as it relates to implementation. |
Conduct Business Risk Analysis
| This step is set up in order to identify high-risk application components that must be tested more thoroughly, and to
identify error-prone components within specific applications, which must be tested more rigorously. |
Define the Tests Objective
This step aims to establish what is to be accomplished as a result of the testing. It ensures that all responsible
individuals contribute to the definition of the test criteria that will be used. The developer of a test plan
determines what is going to be accomplished with the test, the specific tests to be performed, the test expectations,
the critical success factors of the test, constraints, scope of the tests to be performed, the expected end products of
the test, a final system summary report, and the final signatures and approvals. The test objectives are reviewed and
approval for the objectives is obtained. [Lewis, 2008]
|
Describe Testing Approach
The test plan developer outlines the overall approach or how each test will be performed. This includes the testing
techniques that will be used, test entry criteria, test exit criteria, procedures to coordinate testing activities with
development, the test management approach, such as defect reporting and tracking, test progress tracking, status
reporting, test resources and skills, risks, and a definition of the test basis (functional requirement specifications,
etc.). [Lewis, 2008]
|
Define Testing Environment
The test plan developer examines the physical test facilities, defines the hardware, software, and networks, determines
which automated test tools and support tools are required, defines the help desk support required, builds special
software required for the test effort, and develops a plan to support the above. [Lewis, 2008]
|
Develop Testing Specifications
The developer of the test plan forms the test team to write the test specifications, develops test specification format
standards, divides up the work tasks and work breakdown, assigns team members to tasks, and identifies features to be
tested. The test team documents the test specifications for each feature and cross-references them to the functional
specifications. It also identifies the interdependencies and work flow of the test specifications and reviews the test
specifications. [Lewis, 2008]
|
Schedule the Test
The test plan developer develops a test schedule based on the resource availability and
development schedule, compares the schedule with deadlines, balances resources and workload demands, defines major
checkpoints, and develops contingency plans. [Lewis, 2008]
|
Review and Approve the Test Plan
The test plan developer or manager schedules a review meeting with the major players, reviews the plan in detail to
ensure it is complete and workable, and obtains approval to proceed [Lewis, 2008]. These would
encompass incorrect, incomplete, missing and inappropriate information.
|
|
